AutoCom EIE – Data Groups

Data Groups

With few exceptions, data groups must be defined in a device template file in order for them to be available for use on a remote device. Which data groups are defined by a device template file depends on protocol, device type, and unique configuration.

CygNet distributes sample device template files for its EIEs, each of which typically serves one or more hardware models along with applicable firmware. Therefore, the data groups described below are only those data groups defined by CygNet in sample device template file(s). Your template(s) might not include some of the data groups described below. Device template files exist to enable users to customize device configurations; however, CygNet is not responsible for changes made by users.

For information about data group definitions and device template files, see Device Template Files.

For more information about data group dependencies, see Data Group Dependencies.

Note: When an AutoCom EIE data group is in edit mode, a Send only edited items check box displays on the View Data dialog box, and when checked, only the edited values are written to the DDS transaction.

Browse by letter: A B C D E F H L P R S T V

Data Group Type	Usage Notes
Accum	"Accumulators"
Alarms	"Alarms"
AnlgCfg	"Analog to Digital Config"
BaseStroke	"Base Stroke"
BasicPoll	"Basic Poll"
BeamAngle	"Beam Angle Correction"
CfgDg	"Configurable Data Group" See Configurable Data Group.
ComCfg	"Comm Config"
DateTime	"Date and Time"
DevCfg	"Device Config"
DiscCfg	"Discrete I/O Config"
DynaCard	"Dynagraph Card" retrieves and displays surface rod pump cycle data. Data is displayed in table and graph format. You do not need to retrieve any other data group(s) to get dynagraph card data. The total number of card instances that can be displayed per card type varies by card type. See manufacturer documentation for more information. Ordinals associated with the different data group types are hard coded. For instance, ordinal 0 is always Current Card, ordinal 4 is always Start Card, and so forth. Ordinals here do not merely identify the sequence in which "Dynagraph Card" data groups were added to a remote device editor. These "Dynagraph Card" card types are supported by CygNet: Current Card: Specifies the most recent stroke. Custom Card: Specifies one of a large number of AutoCom-specific card types. In the remote device editor, choose a card type after clicking Get from RTU in the data view, or choose a card type using the Custom Card ID UIS command parameter. Ideal Card: Returned from an external system. Calculates an ideal rod pump stroke card based on a set of configuration items. Can be used as a way to compare actual and ideal strokes, and to adjust current configuration to a more ideal state. Pumpup Card: Specifies a card when a unit starts again after having "pumped up". Reference: Specifies a reference or snapshot of a card. Results from reading a reference from a field device or clicking the Save Reference button on a different card type. In AutoCom, this card is known as Snap. Shutdown: Specifies a card when a normal pump-off is detected. In AutoCom, this card is known as Pump off. Start Card: Specifies a card taken when a unit is configured. Used as a baseline. In AutoCom, this is card is known as Base. Click Options > Display Details for table-format plot data and other details. This data group is required if you are connecting a device to the CygNet Dynagraph Viewer client application. However, not all AutoCom-specific card types are supported by the CygNet Dynagraph Viewer.
DynaCardR	"Dynagraph Card (Raw)" enables you to get any of a number of AutoCom-specific card types. Data returned is displayed in raw values; the values are not scaled. This data group is useful for diagnostic purposes.
DynaConfig	"Pumpoff Configuration"
EventCfg	"Event Config"
EventLog	"Event Log"
FluidStrk	"Fluid Stroke Parameters"
HstDly	"History - Daily" enables the collection of 35 days of history.
HstMth	"History - Monthly" enables the collection of 23 months of history. The current month is excluded.
LoadAlm	"Load Alarm Limits"
LoadCalib	"Load Cell Calibration"
LoadDrift	"Load Drift Compensation"
LoadSpike	"Load Spike Detection/Correction"
PosSetup	"Position Setup"
PrdMax	"Production Maximization Info"
PrgCycle	"Program - Cycle-Based" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.
PrgReg	"Program Registers"
PrgStatus	"Program Status"
PrgStroke	"Program - Stroke-Based" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.
PrgTime	"Program - Time-Based" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.
PrgUAct	"Program - User Action" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.
PrgUEvt	"Program - User Event" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.
RunHist	"Run History"
Setpoint	"Set Point"
SingleReg	"Single Register" See Single-Element Data Group.
Status	"Status"
TimeCtl	"Timing Control"
TimeInfo	"Time Information"
ToDateDly	"To-Date - Daily"
ToDateMth	"To-Date - Montly"
Trend	"Trend"
TrendCfg	"Trend Config"
Version	"Version"

Data Group Type

Usage Notes

Accum

"Accumulators"

Alarms

"Alarms"

AnlgCfg

"Analog to Digital Config"

BaseStroke

"Base Stroke"

BasicPoll

"Basic Poll"

BeamAngle

"Beam Angle Correction"

CfgDg

"Configurable Data Group" See Configurable Data Group.

ComCfg

"Comm Config"

DateTime

"Date and Time"

DevCfg

"Device Config"

DiscCfg

"Discrete I/O Config"

DynaCard

"Dynagraph Card" retrieves and displays surface rod pump cycle data. Data is displayed in table and graph format.

You do not need to retrieve any other data group(s) to get dynagraph card data.

The total number of card instances that can be displayed per card type varies by card type. See manufacturer documentation for more information.

Ordinals associated with the different data group types are hard coded. For instance, ordinal 0 is always Current Card, ordinal 4 is always Start Card, and so forth. Ordinals here do not merely identify the sequence in which "Dynagraph Card" data groups were added to a remote device editor.

These "Dynagraph Card" card types are supported by CygNet:

Current Card: Specifies the most recent stroke.
Custom Card: Specifies one of a large number of AutoCom-specific card types. In the remote device editor, choose a card type after clicking Get from RTU in the data view, or choose a card type using the Custom Card ID UIS command parameter.
Ideal Card: Returned from an external system. Calculates an ideal rod pump stroke card based on a set of configuration items. Can be used as a way to compare actual and ideal strokes, and to adjust current configuration to a more ideal state.
Pumpup Card: Specifies a card when a unit starts again after having "pumped up".
Reference: Specifies a reference or snapshot of a card. Results from reading a reference from a field device or clicking the Save Reference button on a different card type. In AutoCom, this card is known as Snap.
Shutdown: Specifies a card when a normal pump-off is detected. In AutoCom, this card is known as Pump off.
Start Card: Specifies a card taken when a unit is configured. Used as a baseline. In AutoCom, this is card is known as Base.

Click Options > Display Details for table-format plot data and other details.

This data group is required if you are connecting a device to the CygNet Dynagraph Viewer client application. However, not all AutoCom-specific card types are supported by the CygNet Dynagraph Viewer.

DynaCardR

"Dynagraph Card (Raw)" enables you to get any of a number of AutoCom-specific card types. Data returned is displayed in raw values; the values are not scaled. This data group is useful for diagnostic purposes.

DynaConfig

"Pumpoff Configuration"

EventCfg

"Event Config"

EventLog

"Event Log"

FluidStrk

"Fluid Stroke Parameters"

HstDly

"History - Daily" enables the collection of 35 days of history.

HstMth

"History - Monthly" enables the collection of 23 months of history. The current month is excluded.

LoadAlm

"Load Alarm Limits"

LoadCalib

"Load Cell Calibration"

LoadDrift

"Load Drift Compensation"

LoadSpike

"Load Spike Detection/Correction"

PosSetup

"Position Setup"

PrdMax

"Production Maximization Info"

PrgCycle

"Program - Cycle-Based" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.

PrgReg

"Program Registers"

PrgStatus

"Program Status"

PrgStroke

"Program - Stroke-Based" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.

PrgTime

"Program - Time-Based" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.

PrgUAct

"Program - User Action" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.

PrgUEvt

"Program - User Event" enables you to read and write custom device-specific programs. Requires a bin.hex data type to accommodate special characters that might be in the data group's string contents. Beam devices only.

RunHist

"Run History"

Setpoint

"Set Point"

SingleReg

"Single Register" See Single-Element Data Group.

Status

"Status"

TimeCtl

"Timing Control"

TimeInfo

"Time Information"